Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split diverse perspectives and inclusion points #171

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

cwilso
Copy link
Collaborator

@cwilso cwilso commented Apr 12, 2024

An attempt to address #169: split out diversity and inclusion to address separately. There is clear overlap, of course, which is why both lists are open-ended.


Preview | Diff

@cwilso cwilso requested review from tantek and wareid April 12, 2024 02:13
Copy link
Contributor

@chaals chaals left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks @cwilso - I think this is an excellent change that addresses the issue raised very well, as well as my initial skepticism regarding aa proposed solution.

Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an improvement.

I'm not sure about the final line "This ensures W3C serves the needs of the entire Web user base." — it seems like an aspirational conclusion rather than stating what we will do (like the previous section's "we will actively seek to be inclusive to all.").

We can iterate on that though.

Copy link
Contributor

@fantasai fantasai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By shifting languages and cultures to diversity of participation and out of diversity of perspective, I think this edit loses that we need people from different cultures, languages, etc. in order to make sure that W3C serves the needs of the entire Web user base. That's a significant regression.

More generally by sorting into two lists we have a problem: diversity of perspective is not limited to things other than personal characteristics; and inclusion needs to also accommodate things like geographic locales and organizational sizes, not just personal characteristics.

To give a few concrete examples:

  • We need people from different languages to ensure that the Web can render all of those languages correctly, not just to be inclusive as an organization.
  • We make efforts to welcome effective participation from small companies with limited resources (not just those at Google/Apple scale), not just because we want their perspective on our work, but because we want W3C to be inclusive across more of society.
  • We need people from different cultures not just to help our organization to be diverse and welcoming, but to ensure that the Web platform can serve the use cases of different cultures.
  • We are struggling with inclusion wrt participants from China not just because of their culture or language, but because they are physically located in China, and that creates problems wrt time zones and wrt access to the critical information so many W3C participants casually store in Google documents that they can't access.

I think it's good to make a point about inclusion and providing a welcoming environment, but splitting hairs about what qualifies as a legitimate axis of diversity in one category or another doesn't seem to be helping.

@cwilso
Copy link
Collaborator Author

cwilso commented Apr 15, 2024

This absolutely is not intended to hairsplit about what is a legitimate axis of diverse opinion vs inclusion; that's precisely why both lists are open-ended ("...and more"). The explicit ask was to split diverse perspectives out from inclusion; yes, some things can certainly be factors in both. Short of having things like language occur in both lists, I don't think this is resolvable, which is why I went with a brief, succinct, and open-ended approach.

@fantasai
Copy link
Contributor

fantasai commented Apr 16, 2024

Both lists are open-ended, but there's no overlap, not even on ones that are particularly relevant to W3C. It supports the argument (that has been made) that some of these are not valid considerations in one list or the other. (Which I disagree with, because I think most if not all of them are valid under both, and we should continue to improve on these items under both.)

fantasai added a commit to fantasai/AB-public that referenced this pull request Sep 30, 2024
This edit pulls some of the improvements of PR w3c#171
without dividing into two separate points with independent
lists of diversity attributes.
@fantasai fantasai mentioned this pull request Sep 30, 2024
@tantek tantek added the Project Vision Vision and Principles label Sep 30, 2024
Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given the lack of consensus in the discussion on this PR, and that no one has raised this as a Statement-blocker (or even a next-note-blocker) either explicitly or implicitly in the comments, I'd like to defer this PR until after we publish an updated NOTE and go for wide review, and solicit wide review comments on the respective issue #169 to see if that demonstrates a strong focus of potential consensus.

I would also ask that any substantial high-level (or philosophical) points about how to solve this issue be instead directed to #169 for discussion there.

Discussion in this PR should preferably be limited to the substance of this specific PR. If there is disagreement on the approach, let's please discuss that in #169. Thanks!

@tantek tantek added Defer Deferred to future work and removed Defer Deferred to future work labels Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defer Deferred to future work Project Vision Vision and Principles
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants